- 
                Notifications
    You must be signed in to change notification settings 
- Fork 607
Implement multi version for apiref #4190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement multi version for apiref #4190
Conversation
b1b95ba    to
    e0bc4a4      
    Compare
  
    | Like this PR, but could we add the update steps into  Aside from that, this LGTM. | 
| Awesome, I’ve been waiting for this feature, thanks, @rikatz. | 
e0bc4a4    to
    c35e936      
    Compare
  
    | @youngnick fixed | 
| /cc @youngnick @robscott | 
| Thanks @rikatz! /approve | 
| [APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rikatz, youngnick The full list of commands accepted by this bot can be found here. The pull request process is described here 
Needs approval from an approver in each of these files:
 
 Approvers can indicate their approval by writing  | 
| This is great, thanks @rikatz! /lgtm | 
What type of PR is this?
/kind documentation
What this PR does / why we need it:
This is an attempt to implement multiversion for our API Reference.
While it is very "rudimentary", it allows us to set different versions of API on the navigation bar.
The rationale about keeping just the current versions (1.3, 1.4 and main) is because before 1.3 we didn't had experimental APIs and I've tried to not overcomplicate it.
Once a new release is cut, the release manager or some contributor must:
generate.shto add the new branchWhich issue(s) this PR fixes:
Fixes #4151
Does this PR introduce a user-facing change?: